1. Spawn links don't generate the clones. They simply make a wormhole to get the clone onto the battlefield.

2. We have no assets to add on backpacks to clones.

3. What's stopping this from being put on a scout? Doesn't a link that can cloak and shoot back and is controlled by a player seem a little OP?

4. Mobile CRUs barely work on vehicles, I don't want to know what chaos they'd cause on infantry. Imagine a whole team that spawns inside a wall and gets stuck because the link person is too near a wall.

Before we get too caught up in what the CPU/PG and ISK cost of this hypothetical item might be it'd be nice I think to find out if something is even plausible in terms of coding.

As far as I know the mCRU code is a mess and we'd need CCP weigh in on if this idea could commandeer the current drop uplink code.

Also a suggestion instead of Uplink Backpack maybe just call it a Mobile Uplink?

Honestly, I could almost see this as something that logistics dropsuits have built-in like the logi dropships of old.

I like the idea overall, but would we have to look at equipment slots? If we build it into the Logiframe, that is giving Gal/Min logis essentially 5 equipment slots at proto. If we did build it in, I think we would have to cut the CPU/PG comparatively or take a slot away (similar to the built in cloak idea for scouts). Also, would Std/Adv/Pro suits have the same parameters (flat 5-7 second spawn time) or would we tier it based on level?

I agree on the module slot. Steal the mcru code, add it to an uplink, rename it and have it work either with an activation or automatically, with no additional graphics needed. The sound idea is also a possibility. If we want to increase their EWAR as was suggedted so they are scanned by, well, basically anything as a negative, that could be a good drawback to offset the various benefits.

I'm on my phone so can't type as fast ad you. Lol. I do think the 20 seconds at std seems a bit high. Even a standard uplink has lower spawn times than that. Is this because it is unlimited, you want it to have an additional drawback?

So would it be limited to one spawn per activation or as many people as can start their spawn in the alloted time? Is there a reason it wouldn't be able to remain actve like a regular uplink or MCRU?

Agree on location of spawn. It should always be behind. That just makes sense.

Wait, you're suggesting that i stay still, visible to every doodad to see, defenseless while i wait 15 seconds for a ******* blueberry to spawn? that's rediculous. Unless we can spawn in capital class suits with it. AND other teammates can teleport to you, at no cost to them. While alive. You can't say "let's add something to the game then nerf it to ****" that's not how development works.

Im gonna put bandwith numbers out for the current suits:

Scouts:
-STD= 6 MB
-ADV= 9 MB
-PRO= 12 MB

Assaults:
-STD= 8 MB
-ADV= 12 MB
-PRO= 16 MB

Logis (lowest bandwith numbers):
-STD= 16 MB
-ADV= 24 MB
-PRO= 32 MB

So with a bandwith required of 15MB the only suits that could use this would be Logis and proto assaults. A drop uplink for example requires 4MB each. With the current meta a proto scout can deploy 3 links, assault 4 and a logi can deploy 8 at a time. It would deffo come in handy in PC for people who play assault but dont want to bother with the deployment of proto links.

Overall this would be copy pasting spawning on squadmates like you can on battlefield. Im sure this is possible though it would suffer from the same issue mobile CRU's have and that is that you cannot select them when you havent bleed out yet.

Ok, so some things i'd like to suggest. The "Uplink Backpack" should work somewhat differently to what the current uplinks do. I agree with the claim that active unlimited spawns on any one player plus allowing them to extensively tank a fit would be rather OP. The fitting costs for this link SHOULD be high across tiers, all links at each tier should somewhat mimic those of the normal uplinks but should have a lower percentage of spawn time modifier at each tier (say, 5-10% lower) OR they could have the highest spawn time modifier percentage available at each tier. Also, I think it'd be best that this module would become an equipment module similar to the cloak that you could activate and deactivate at will. While active the link would boost the users profile to make him easier to spot and have a set maximum number of spawns per each active period and then require a cooldown period before reactivation, the spawns would still be infinite but would require the user to decide when to use this module rather than having it active the whole match. Not to mention that if spawns were unlimited 24/7 a well made squad could protect the user of this link and gain complete swarm control over an extended period completely negating the profile increase drawbacks (hell, they'd probably use the logi as bait and tackle all enemies foolish enough to attempt a move against the logi). This link should NOT limit your movement in the slightest, maybe a small mobility delay at the time of an allied spawn but that's it, the high fitting costs wouldn't make it impossible to fit it on other suits, but the logi bonus would make it easier to fit. The bandwith required to use this link should be set in a way that makes it more effective to use it on a logi, 14-16 BW seems okay to me. Though I don't like locking a class out of potential new content I can see the issues with a link moving at 10-11m sprint speed , however let's not forget that logi's also use nanohives, having such a high bw cost would mean that activating this module would likely destroy some of their deployable equipment for lower tiered logi's so that's something to consider. Also, about MCR+Ü's, you should all know that there're some places where vehicles can't/shouldn't get into. By limiting the number of spawns per active duration and requiring a cooldown after each spawn session is completed it means that this link won't be as reliable as an MCRU because there's no telling when the user will decide to pull the plug on the link while the MCRU would be a spawn inside a highly armored/shielded vehicle that is more than likely to survive long enough for you to spawn... though MCRU's would need to work first. Just my 2 ISK.

As some have suggested anyone spawning on a merc equipped with this link should always spawn behind him. Also, while active they should make a similar sound as the "hum" drop uplinks make, maybe a muffled version of it.

P.S. HAIL O GLORIOUS WALL OF TEXT!

TL;DR: As a penalty, while active make the users scan profile go slightly up and make them emit the "hum" of drop uplinks and make it an equipment that you activate and deactivate at will with a set number (say 5-10) of maximum spawns and once those spawns are up make the link require a cooldown/recharge period before it can be used again (similar to how the cloak works) to prevent exploitation of constant unlimited spawns. Also make it's stats similar to that of current drop uplinks with minor tweaks and give them a spawn time modifier that is either lower or higher than the current drop uplinks at each tier.

I think the most important thing I'm reading here is no one is opposed to the idea of spawning on infantry. Looks like the debate is fitting cost more than anything.

It seems that using uplik code would be the best bet. I did some testing and the logic behind where to spawn for uplinks seems pretty robust and likely going to be lest glitchy since you can't throw a merc under a crate. :)

I am in agreement with the general thoughts on the thread. The bw + fitting seem to be the points of conversation. I agree on the "spawn behind always" is a solid idea.

The only other point of conversation is whether it is permanently active like an uplink or something that has to be turned on/off a la a cloak. I think both ideas could be acceptable given we have the fitting costs/ISK costs etc. set to be comparable. Maybe have 2 seperate ones, 1 always on and 1 that has to be turned off/on, similar to regular and triage nanohives. There isn't really a need fir a "one or the other mentality."

Might be a little excessive. I don't think the people playing are going to want to wait for the spawn and then sit and wait on the RDV to drop them down. Most likely they will get hung up in the air by their head and get slapped around until they get either get killed or someone comes up and shoots them while hanging from the RDV. It would be funny but I don't think the people spawning would appreciate it.

I think the main idea behind being able to turn the module on and off would be to manage bandwidth if needed.